MS licensing on Sharepoint is as easy as licensing gets. It can't be more straightforward.

https://products.office.com/en-us/sharepoint/sharepoint-licensing-overview

"For On-Premises, intranet sites are licensed using a Server/CAL (Client Access License) model. SharePoint Server 2019 is required for each running instance of the software, and CALs are required for each person or device accessing a SharePoint Server."

It's that simple. CALs are requires for each person or device accessing SP. That's it. Nothing more or less. It's not just easy, but exactly what you'd logically expect the licensing to do if they were being rational.

@IRJ said in Windows Server 2012 R2 - Share Auditing for Changes:

I know you use wazuh..

Check this out

https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity/index.html

Thanks! Checking out setting this up. Hopefully, it will reveal the culprit.

@black3dynamite said in Salt - Can't Connect to Minions After Adding Them to Master:

I sometimes have to add --timeout 60 so I can see a response
salt FP01.domain.local test.ping --timeout 60

Seems to be working. I think that it was the firewall needing the exception AND using the

Thanks!

@ilyas said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell:

@scottalanmiller

Hi, Thanks for wonderful script that save my time.
Could You please guide me how we can run this script on multiple servers?

I tried foreach PowerShell method but it does not work.

From the ISE, load the script and then enter-pssession for each system. Once connected, run the script from the ise. Sorted.

@black3dynamite said in Windows Server 2019 Need to Download and Run without AV Deleting Files:

https://www.thomasmaurer.ch/2016/07/how-to-disable-and-configure-windows-defender-on-windows-server-2016-using-powershell/

For now, just temporary disable Real-Time Protection via PowerShell
Set-MpPreference -DisableRealtimeMonitoring $true

Download the executable and scan it manually before you install
Start-MpScan -ScanPath C:\datastore\file.exe -ScanType QuickScan

Enable Real-Time Protection after the install
Set-MpPreference -DisableRealtimeMonitoring $false

Excellent, now THAT did it.

@scottalanmiller said in Windows Server 2019 Basic Installation:

@dbeato said in Windows Server 2019 Basic Installation:

@Obsolesce said in Windows Server 2019 Basic Installation:

@scottalanmiller said in Windows Server 2019 Basic Installation:

@Obsolesce said in Windows Server 2019 Basic Installation:

@scottalanmiller said in Windows Server 2019 Basic Installation:

@JaredBusch said in Windows Server 2019 Basic Installation:

The current install method brings Windows Server on parity with the Linux ecosystem really. You install, choose some options and end up at a prompt after reboot. Then you remotely add the features and shit you want.

Yeah, very in like with Fedora, Ubuntu, or Deepin. Deepin might still be my favourite installer for normal stuff of the four.

Did you have a Deepin install screenshot chain on here?

No, but I do it so often, it would be easy to get.

That'd be nice to see on here.

Last post on it was below
https://mangolassi.it/topic/14453/deepin-linux-15-4-1-install

The install still looks like that.

LOL that's not an installer. That's a push button, get peanuts.

Nice though.

@pmoncho said in The Hidden Cost of Licensing Windows Server - Activation:

@scottalanmiller said in The Hidden Cost of Licensing Windows Server - Activation:

Just looking at this with a customer that just put in a new Windows 2019 server. The machine was purchased with a volume license agreement for Server 2019 Standard. Everything should be super easy, in theory. Problem is, license key from the volume license center doesn't work. We spend a bit of time trying to get this to apply, but no luck.

I have run into a similar situation this morning and not being able activate the VLSC liscense.

Before I decided to call MS and getting frustrated, I was able to activate from an elevated command line.
cscript c:\windows\system32\slmgr.vbs /ipk <product key>

Throwing this out here in case someone comes along this post at a later time.

I've heard that that often works. We had tried that in our case and it had failed.

@Reid-Cooper said in General Guidance on Windows Admin Center WAC:

@Obsolesce said in General Guidance on Windows Admin Center WAC:

Yes you do need to either add other devices manually or by importing a list... but it's a one-time thing so it's a non-issue IMHO.

Not bad for tiny environments. But at any scale, how does that handle machines being added in the future? You have to manually add every new machine after every change to WAC?

I've only had about 100 servers and a handful of Win10 in it, so I'm not familiar with handling that at scale. It really only requires a txt file of a list of devices which is simple to maintain in any aspect. I only had to import that to get everything back in. If I added a new server, I would add it to the text file then add that server.

Our go-to solution for VSS problems is to set up a dedicated snapshot volume. Otherwise we were getting timeouts and M$ does ugly things that don't make sense when VSS doesn't work properly.

@wrx7m said in PowerShell - Off-boarding Script:

@dafyre said in PowerShell - Off-boarding Script:

@wrx7m said in PowerShell - Off-boarding Script:

@dafyre I think I found where you got it - https://www.powershelladmin.com/wiki/Powershell_prompt_for_password_convert_securestring_to_plain_text

Anyway, I am not sure where, in my script, I should place that function.

You'd put the actual function at the top of your script, and then just

$myPassword=convertFrom-SecureToPlain -securepassword $MySecurePassword

Wherever you need the password in plain text form.

Thanks. It mostly works. The only problem is that it isn't actually using the password I specify at the top. It is somehow generating its own and then writing it at the end. I put in

write-host "Plain Text Says: $plainText"

and it shows the password that I typed in for the secure variable at the beginning, followed by the one that it generated.

Plain Text Says: $#@%4#@177 Jof91348

Works fine for me here.... Check and make sure you don't have an extra write-host or anything somewhere.

4a0db1d0-785c-4771-9ad2-9cec6cb0434a-image.png

@Emad-R said in Download Windows Server 2019:

@scottalanmiller

https://software-download.microsoft.com/download/sg/17763.253.190108-0006.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

Thanks @Emad-R with this link you don't have to go through all the paperwork.

@gjacobse said in Add a User to Remote Desktop Users in Windows Remotely:

I seem to remember doing this via ScreenConnect CMD

Only works if SC is installed, which if it was, we'd not need to do it 🙂

Not yet.

@scottalanmiller lol